Update Privacy Pools vendor file to reflect v1 deployment#92
Open
0xmikemcc wants to merge 2 commits intoethereum:masterfrom
Open
Update Privacy Pools vendor file to reflect v1 deployment#920xmikemcc wants to merge 2 commits intoethereum:masterfrom
0xmikemcc wants to merge 2 commits intoethereum:masterfrom
Conversation
- Replace vendors/privacypools.md with accurate v1 deployment info - Add viewing keys, enterprise use cases, progressive ASP decentralisation - Add Privacy Pools to private payments approach and vendor recommendations - Add cross-references in L1 ZK commitment pool and shielding patterns - Add Association Set and ASP glossary entries
Meyanis95
reviewed
Feb 25, 2026
| - [Shielded ERC-20 Transfers](../patterns/pattern-shielding.md) with commitment/nullifier schemes | ||
| - Higher per-transaction costs but battle-tested infrastructure | ||
|
|
||
| **L1 Compliance-Friendly Shielding (Privacy Pools):** |
Collaborator
There was a problem hiding this comment.
I suggest that instead of having a new category, we add an extra bullet point to the above.
- Extends the shielded pool model with association set proofs for regulatory compliance signaling with Privacy Pools
Meyanis95
reviewed
Feb 25, 2026
|
|
||
| ## See also | ||
| - pattern-dvp-erc7573.md · pattern-regulatory-disclosure-keys-proofs.md | ||
| - Privacy Pools (vendor): ../vendors/privacypools.md — production L1 implementation of this pattern with compliance extensions |
Collaborator
There was a problem hiding this comment.
Can we add a link instead?
Privacy Pools (vendor):
Meyanis95
reviewed
Feb 25, 2026
| - Railgun: https://docs.railgun.org/wiki | ||
| - Aztec docs: https://docs.aztec.network/ | ||
| - Zama fhEVM: https://docs.zama.org/protocol/protocol/overview | ||
| - Privacy Pools: https://privacypools.com (compliance-friendly shielded pool with association set proofs) |
Collaborator
There was a problem hiding this comment.
The description in parentheses is redundant with line 27.
Meyanis95
reviewed
Feb 25, 2026
|
|
||
| **Association Set**: A defined subset of deposits in a shielded pool, constructed by an Association Set Provider (ASP) according to compliance policies (e.g., excluding sanctioned addresses). Users prove membership or exclusion in an association set during withdrawal to signal compliance without revealing their specific deposit. | ||
|
|
||
| **Association Set Provider (ASP)**: An entity that defines, computes, and publishes association sets for a shielded pool. ASPs apply screening rules (sanctions lists, chain analytics, KYC credentials) to classify deposits and publish the resulting set as a Merkle root that users can prove against. |
Collaborator
|
Thanks for the PR @0xmikemcc You can run the linter locally with the following: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The current
vendors/privacypools.mdwas written from the 2023 SSRN paper, not the actual v1 deployment. This PR updates it to reflect the production state and adds cross-references across the repo.Key issues fixed:
ameensol/privacy-pools(research repo) instead of0xbow-io/privacy-pools-coreChanges:
vendors/privacypools.md— Full rewrite with:approaches/approach-private-payments.md— Added:patterns/pattern-l1-zk-commitment-pool.md— Added vendor cross-reference to Privacy Pools in See alsopatterns/pattern-shielding.md— Added:GLOSSARY.md— Added definitions for:Context
This PR is submitted by 0xbow, the developer and operator of the Privacy Pools protocol. We want to ensure the IPTF map accurately represents the current production state of the protocol for institutional evaluators.